Rewrite FAQ paradigm answer and improve clarity - #21

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

PR Review: FAQ Paradigm Rewrite

Overall this is a focused, well-scoped documentation PR. The changes improve clarity and conciseness throughout.

Positives

• Q0 HOW/WHAT/WHETHER framing is memorable and genuinely clarifies the paradigm concept
• Q1-a: adding a CQRS definition before the Be-specific commentary helps readers unfamiliar with the pattern
• Q23 property ordering: moving properties before the constructor is idiomatic PHP 8.x for readonly classes. Correct fix.
• Removing the subjective "Interestingly..." paragraph (Q1) and the Q2 cross-reference in Q11 are clean cuts.

Issue: Q0 — Implicit answer to an explicit question

The question is "Is this a new programming paradigm?" The original answered "Yes." explicitly. The rewritten answer defines what a paradigm is and demonstrates that Be qualifies, but never states the affirmative. A reader could finish without a clear conclusion. Consider leading with it: "A. Yes — and in a specific sense. A pattern is a better answer to an existing question. A paradigm changes the question itself."

Issue: Q2 — Lost motivating contrast

The removed paragraph explained why Be differs from OOP by contrasting original intent vs. common practice ("objects become obedient data containers"). The one-sentence replacement states what Be does but loses the contrast that makes it meaningful. This content was load-bearing for readers asking "OOP already claims autonomy — why is Be different?"

Issue: Q16 — "Why" removed

The deleted sentence — "Persistence and external communication are implementation details, not user concerns" — gave the design rationale for confining DB/API work to Reason. The current version communicates the benefit (freed from schemas) but omits the principle. For a philosophy-forward framework, the principle is often what readers need to internalize.

Minor

Blank line before --- in Japanese frontmatter: a blank line was added between permalink: and --- in ja/14-faq.md. Jekyll tolerates this, but it is inconsistent with the English file and every other page in the repo.

No concerns on security, performance, test coverage (documentation-only changes), or Jekyll build compatibility.